sql/analyzer/prune_columns.go: Turn off pruneColumns when a Subquery expression exists. #314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…xpression exists.
zachmu
approved these changes
Feb 25, 2021
sql/analyzer/prune_columns.go
Outdated
| // We do not run pruneColumns if there is a Subquery | ||
| // expression, because the field rewrites and scope handling | ||
| // in here are not principled. | ||
| plan.Inspect(n, func(n sql.Node) bool { |
There was a problem hiding this comment.
plan.InspectExpressions is what you want here
reltuk
changed the title
Hydrocharged
deleted the
aaron/avoid-pruneColumns-with-subquery-expression-below-node
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.